Dev_Tasks
Level 1 and 2 Logicmaster passwords, which prevent write access, cannot be used in applications that include COMMREQs. COMMREQs require write access to return their completion status.
Reference: Series 90-30 Genius Bus Controller.
#END#

Wait_Flag	
This flag determines whether PLC will wait until the device serial ports receive the intended data before continuing. The request can either send a message and wait for a reply, or send a message and continue without waiting for a reply. If the Command Block specifies that the program will not wait for a reply, the Command Block contents are sent to the device and ladder program execution resumes immediately. This is referred to as NOWAIT mode. If the Command Block specifies that the program will wait for a reply, the Command Block contents are sent to the targeted device and the CPU waits for a reply for a maximum length of time specified in the Command Block. If the device does not respond in that time, ladder program execution resumes. This is referred to as WAIT mode.
#END#

Idle_Tmout	
The idle timeout value is the maximum time the PLC waits for the device to acknowledge receipt of the request. For NOWAIT, this value is not used. (Any timeout value is ignored; it can be zero.) If WAIT is selected, this word specifies the idle timeout period, in 100-microsecond increments.
#END# 

Max_Comm_Tm	
This word contains the maximum amount of time the program should hold the window open when the device is busy. For NOWAIT, this value is not used. (Any timeout value is ignored; it can be zero.) If WAIT is selected, this word specifies the maximum time in 100 microsecond increments.
#END#

Enable Disable Outputs
This can be sent to GBC to disable sending O/Ps to any block. This overrides configure parameter O/Ps enable/disable at start. For e.g., if O/P were initially disabled to all blocks during configure, this could be used to enable O/Ps to specific devices/to all devices.
#END#

Dequeue Datagram	
The Bus Controller handles most incoming datagrams automatically, with no additional programming required. Under certain circumstances, however, the Dequeue Datagram command must be used to transfer incoming datagrams to the CPU. Program the Dequeue Datagram command for the following: 
1.Replies that are received after sending Reply-type datagrams with the Send Datagram command. (If Send Datagram with Reply is used instead, it automatically handles replies).
2. Unsolicited datagrams that are not recognized by the Bus Controller (Function Code not 20).
#END#

Send Datagram	
1.Datagrams for which no COMREQ command number is defined, such as Begin Packet Sequence, End Packet Sequence, and Write Point.
2. Read Device and Write Device datagrams that are broadcast, but which should be ignored by another Series 90-70 Bus Controller.
3. Datagrams that must be guaranteed transmission during the next bus scan. This should be done with restraint, for the reasons explained on the following pages.
4. Datagrams which do not cause another device to send back a reply, such as Pulse Test, or Write Configuration.
5. Messages that the 90-70 GBC has COMMREQs for, but the 90-30 GBC does not.
Datagrams which DO cause another device to send back a reply, such as Read Diagnostics or Read Configuration, are usually programmed using their assigned COMREQ numbers or the Request Datagram Reply command (COMREQ #15). However, if Send Datagram is used to send datagrams that cause replies, the Dequeue Datagram command must be used to transfer the replies back to the CPU.
#END#

Request Datagram Reply
The Request Datagram Reply command can be used to send any datagram that causes the target device to return a reply, such as: Read Configuration or Read Diagnostics. With this command, the Bus Controller automatically transfers replies to the CPU; no separate Dequeue Datagram command is needed to handle them. These datagrams are normally programmed using their assigned COMREQ command numbers. The primary reason for sending any of these datagrams using COMREQ #15 would be to assign it high priority, guaranteeing that it would be sent on the next bus scan. Before doing this, see COMREQ #14: Send Datagram for important information about datagram priority.
#END#

Device_Number
Enter 0-31 for one block.
#END#

Enable_OR_Disable_Outputs	
Choose Enable/Disable
#END#

Maximum_Data_Memory_Length	
Bit/ word value (depends on the memory type selected). This tells CPU how much memory will be needed to store all data. If length of data returned exceeds this length, GBC writes as much data as possible to CPU & returns data error to COMMREQ status location
#END#

Memory_Type	
Enter the memory type where the GBC will place the data in the CPU.
#END#

Sub_Function	
Select the sub function
#END#

Priority	
A Bus Controller can send one datagram per bus scan. Therefore, during one bus scan, there may be one normal priority datagram followed by up to 31 high priority datagrams, or up to 32 high priority datagrams sent by the devices on the bus. In one bus scan (one complete rotation of the bus token among all devices on the bus), there can be just one normal priority datagram sent by any device. If a normal priority datagram or similar system message (such as a fault report) has already been sent by any device (including itself), a device must wait until its next turn on the bus before it can send a normal priority datagram.
#END#

Datagram_Length	
Enter the actual length of the Datagram
#END#

Datagram_Content	
Enter the entire datagram. If Send Datagram command is used to broadcast a Write Device datagram, and that datagram should be IGNORED by another Series 90-30 GBC, set first byte of the datagram (this byte is normally 0), to FE hex.
#END#

Sub_Function_Of_DG_To_Send	
Select the sub function of Datagram to be send
#END#

Datagram_Length_15	
Enter the actual length of the Datagram
#END#

Sub_Function_For_Reply	
Select the sub function of Reply
#END#

Function
Function code is always 32.
#END#

Memory_Type_For_Reply	
Enter the memory type 
#END#

Memory_Offset_For_Reply
Starting address within this memory type.
#END#

Maximum_Data_Memory_Length_DG	
Enter a value in bits or words, depending on the memory type selected. This entry tells the CPU how much memory will be needed to store all the reply data. The length depends on the message and device type. If the length of the memory is smaller than the amount of reply data received, the extra portion of the data will be lost, and a data error (16) will be returned to the status location.
#END#

Datagram_Content_DG
Enter the entire datagram.
#END#
